Release 10.1A: OpenEdge Getting Started:
WebSpeed Essentials

Setting environment variables

Environment variables required by WebSpeed are set during installation in the ubroker.properties file. You might need to set the PROPATH and other standard environment variables (for example, DLC) on the WebSpeed Transaction Server machine.

Note: In distributed configurations, you must edit the appropriate environment variables on each machine where you have WebSpeed components installed.

You can change most of these settings using the Progress Explorer or by editing the WebSpeed property file, ubroker.properties. Note that it is not necessary to modify the Windows registry or the system environment variables (through the Windows Control Panel).

PROPATH and other standard OpenEdge environment variables

When you install the WebSpeed Transaction Server, the installation process sets the PROPATH for you in the ubroker.properties file. The PROPATH initially includes a number of subdirectories in your installation directory. In addition, the PROPATH includes a dot ( . ) directory reference. When the agent sees the dot, the process substitutes the name of its current working directory. For example, the agents resolve the dot to their broker’s default directory, which is the working directory.

You can override installed PROPATH settings using the PROPATH property in the properties file (ubroker.properties).

Working directory settings

The properties file relies on a default setting for the working directory that you specify during installation. You can remove or modify the references in the properties file to establish your own working directory settings for both the WebSpeed Transaction Server and the NameServer.

For more information on OpenEdge environment settings, see OpenEdge Getting Started: Installation and Configuration .

Configuring WebSpeed and NameServer log files

For disk management reasons, you might want to specify a nondefault location for the log files used by WebSpeed. A WebSpeed installation uses a number of different log files, which are stored in the default working directory. For example:

[TransactionServername.]server.log — WebSpeed Transaction Server log file set using the srvrLogFile property in the [Ubroker] section of the properties file.
[TransactionServername.]broker.log — WebSpeed broker log file set using the brokerLogFile property in the [Ubroker] section of the properties file.
[NameServername.]ns.log — NameServer log file set using the srvrLogFile property in the [NameServer] section of the properties file.

After you decide where you want the log files to reside, you can specify the location for each in the Progress Explorer or by directly editing the ubroker.properties file. For more information, see the "WebSpeed administration" section.

Because the log files receive the WebSpeed and NameServer startup and shutdown messages, OpenEdge system messages, and trace messages, the files can grow quickly. If you have the Append option set in the Transaction Server’s configuration, these log files do not truncate automatically. In this case, you should periodically trim the files with a text editor. You might want to archive the contents of the files as you do it. For more information on maintaining log files, see the "Maintaining the WebSpeed Transaction Server and NameServer log files" section.